fix(ingestion): report the import environment from the heartbeat asset - #838

database_connectivity fails in Dagster+ with ModuleNotFoundError: No module named 'db', while the code location loads and ingestion_heartbeat runs.

Two attempted fixes have not worked — inserting the repository root from
automated_ingestion/__init__.py, and setting PYTHONPATH=/opt/dagster/app.
So the assumption behind both is wrong somewhere I cannot see from outside the
container.

What has been ruled out

• db/ is missing from the image. It is not. I rebuilt the image locally
  from the same template and context (context: ./, .dockerignore excludes
  only .venv) and /opt/dagster/app/db is present.
• The code is wrong. In that same image, find_spec('db') resolves and
  from db.transducer import TransducerObservation succeeds.
• A missing dependency masquerading as db. In the image, an absent
  dependency names itself — No module named 'sqlalchemy', not 'db'.

The remaining explanation is that in the step process, automated_ingestion
resolves from somewhere db does not. My local check ran python -c, which
puts the working directory on sys.path; Dagster runs a console script, where
it does not. That is a real difference and I cannot see which paths the step
process actually has.

What this adds

ingestion_heartbeat now reports cwd, the resolved app root and its
contents, whether db and domain are findable via find_spec, and the
full sys.path. It needs no credentials and no database, so it reports even
when everything else fails.

Materializing it answers the question directly instead of another round of
inference.

PYTHONPATH is also added to the setup script's storage phase — harmless if
it turns out not to be the cause, and correct regardless.

🤖 Generated with Claude Code